---
title: Quickly Connect Dify to Slack, Lark, Discord, Telegram and Other Platforms
---

## 1. Overview

There are various IM platforms in the market, each with different methods for bot integration and varying levels of difficulty, making it challenging to quickly connect to LLMOps platforms like Dify and leverage its powerful ecosystem. With [LangBot](https://github.com/RockChinQ/LangBot), you can quickly integrate Dify with platforms such as QQ, WeChat, Feishu, DingTalk, Telegram, Discord, and Slack to provide services. Additionally, LangBot offers extension mechanisms and a rich ecosystem to flexibly meet your needs.

## 2. Deploying LangBot

### 2.1. Deploying LangBot

You can deploy LangBot in three ways:

1. Docker deployment: [Link](https://docs.langbot.app/en/deploy/langbot/docker.html)
2. Manual deployment: [Link](https://docs.langbot.app/en/deploy/langbot/manual.html)
3. Deployment using aaPanel: [Link](https://docs.langbot.app/en/deploy/langbot/one-click/bt.html)

### 2.2. Connecting to Messaging Platforms

Refer to [this page](https://docs.langbot.app/en/deploy/platforms/readme.html) to choose your messaging platform, such as Slack, Lark, DingTalk, Telegram, Discord, etc.

## 3. Integrating with Dify

LangBot uses `Pipelines` to control message processing. When first started, LangBot automatically creates a default pipeline. Go to the pipeline configuration page and click to open the pipeline configuration.  
Select the `AI` tab and switch the runner to `Dify Service API`.

![](https://assets-docs.dify.ai/2025/05/216b4607dd3dd7702a43fed190e016f4.png)

Fill in your Dify service's API endpoint address, Dify application type, and API Key. After completion, you can chat with the bot in your instant messaging software.

When using workflow applications, please use `summary` as the key to return workflow execution results.

![](https://assets-docs.dify.ai/2025/05/5ca053769ccf6b39cc916916c06b4368.png)

When using workflows, LangBot will explicitly pass the following parameters, which you can add in the start node of your Dify workflow:

- `user_message_text`: Plain text of user message
- `session_id`: User session ID, `person_<id>` for private chats, `group_<id>` for group chats
- `conversation_id`: String, user session ID generated by LangBot. Regenerated when user resets session
- `msg_create_time`: Numeric type, timestamp (in seconds) when message was received

You can [customize any variables through plugins](https://docs.langbot.app/en/plugin/dev/api-ref.html)

![](https://assets-docs.dify.ai/2025/05/28522dd204fee0553943ae1e0bba9bb6.png)

- For detailed instructions, please refer to the LangBot documentation

## 4. Demo

> Below shows Discord and Slack examples only. Other platforms like Lark, DingTalk, Telegram can also be integrated

![](https://assets-docs.dify.ai/2025/05/2014d463b6d44446422ac7e23483212a.png)

![](https://assets-docs.dify.ai/2025/05/3317a7a3f29798cc18bfb5037a7eec07.png)

{/*
Contributing Section
DO NOT edit this section!
It will be automatically generated by the script.
*/}

<CardGroup cols="2">
    <Card
        title="Edit this page"
        icon="pen-to-square"
        href="https://github.com/langgenius/dify-docs-mintlify/edit/main/en/learn-more/use-cases/connect-dify-to-various-im-platforms-by-using-langbot.mdx"
    >
        Help improve our documentation by contributing directly
    </Card>
    <Card
        title="Report an issue"
        icon="github"
        href="https://github.com/langgenius/dify-docs-mintlify/issues/new?title=Documentation%20Issue%3A%20ct-dify-to-various-im-platforms-by-using-lang&body=%23%23%20Issue%20Description%0A%3C%21--%20Please%20briefly%20describe%20the%20issue%20you%20found%20--%3E%0A%0A%23%23%20Page%20Link%0Ahttps%3A%2F%2Fgithub.com%2Flanggenius%2Fdify-docs-mintlify%2Fblob%2Fmain%2Fen/learn-more/use-cases%2Fconnect-dify-to-various-im-platforms-by-using-langbot.mdx%0A%0A%23%23%20Suggested%20Changes%0A%3C%21--%20If%20you%20have%20specific%20suggestions%20for%20changes%2C%20please%20describe%20them%20here%20--%3E%0A%0A%3C%21--%20Thank%20you%20for%20helping%20improve%20our%20documentation%21%20--%3E"
    >
        Found an error or have suggestions? Let us know
    </Card>
</CardGroup>
